Rest API Status is not changed from Acknowledge to Trigger

#1

Hi,

We are using the Rest API for incidents. We are facing issues while changing the status from “Acknowledged” to “Triggered”.

E.g. The incident is created, then its status is changed to “Acknowledged”. Now we are trying to change its status to “Triggered”.

Following is the data:
API documentation: https://api-reference.pagerduty.com/#!/Incidents/put_incidents_id
sample request body:
{
“incident”: {
“type”: “incident_reference”,
“status”: “triggered”
}
}

or
API documentation: https://api-reference.pagerduty.com/#!/Incidents/put_incidents_id
sample request body:
{
“incident”: {
“type”: “incident_reference”,
“status”: “unacknowledged”
}
}

Kindly let us know how to change the status to “Triggered” using Rest API?

Thank You

Regards,
Sonal

#2

Hi Sonal,

When updating an incident with this endpoint, the new status of the incident can only be resolved or acknowledged.

As a possible solution to re-trigger this incident with this REST API endpoint, reassigning or delegating the incident by updating the appropriate field would cause the incident to re-trigger.

I would also be happy to relay feedback to the team about wanting to use this endpoint to update incident’s "status": back to triggered

#3

Hello,

This option we can do from PagerDuty web UI where by unacknowledging incident status is changed back to trigger.

But same thing we are not finding any way from API, so is this API limitation as of now ?

Rest API Status is not changed from Acknowledge to Trigger
#4

Our REST API docs specify that resolved and acknowledged are the only statuses you can set as the new status of the incident:

rest_api

However, I did some testing and found a workaround here. It appears that you can update from “acknowledged” to “triggered” status if something else changes as well. For example, if you set or update the incident priority in addition to updating the status to “triggered”, you should see both changes take effect.

1 Like